Channel mapping in shared spectrum in the presence of higher tier users

ABSTRACT

Techniques and apparatus for channel mapping in shared spectrum in the presence of higher tier users are provided. One technique includes evaluating, for different channel locations of orthogonal channel(s) within available spectrum, an amount of transmission limitation imposed to a group of devices due to incumbent protection, an amount of available bandwidth, and/or a maximum contiguous channel size. A channel location is assigned to each orthogonal channel, based on the evaluation. Another technique includes determining first channel location(s) in order to assign at least a first orthogonal channel within available spectrum. Each first orthogonal channel is associated with a group of devices sharing bandwidth within one or more networks. An exchange is participated in with a network entity to share a first set of information associated with the first channel locations. A determination is made whether to modify portion(s) of the first set of information, based on the exchange.

CROSS-REFERENCE TO RELATED APPLICATIONS & PRIORITY CLAIM

This application is a divisional application of U.S. application Ser. No. 16/018,027, filed Jun. 25, 2018, which claims benefit of and priority to U.S. Provisional Patent Application No. 62/525,413, filed Jun. 27, 2017, and U.S. Provisional Patent Application No. 62/545,991, filed Aug. 15, 2017, all of which are assigned to the assignee hereof and hereby expressly incorporated by reference herein as if fully set forth below and for all applicable purposes.

TECHNICAL FIELD

Aspects of the present disclosure relate generally to wireless communications and, more particularly, to techniques for allocating (or assigning) channel locations to channels used by different groups of wireless nodes. In embodiments, channels may be orthogonal and may by dynamically assigned in the case of co-channel coexistence between different groups and interference to one or more other wireless nodes.

INTRODUCTION

Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, video, and the like, and deployments are likely to increase with introduction of new data oriented systems such as Long Term Evolution (LTE) systems. Wireless communication systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth and transmit power). Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, 3GPP Long Term Evolution (LTE) systems, and other orthogonal frequency division multiple access (OFDMA) systems.

Generally, a wireless multiple-access communication system can simultaneously support communication for multiple wireless terminals (also known as user equipments (UEs), user terminals, or access terminals (ATs)). Each terminal communicates with one or more base stations (also known as access points (APs), eNodeBs, or eNBs) via transmissions on forward and reverse links. The forward link (also referred to as a downlink or DL) refers to the communication link from the base stations to the terminals, and the reverse link (also referred to as an uplink or UL) refers to the communication link from the terminals to the base stations. These communication links may be established via single-in-single-out, single-in-multiple out, multiple-in-single-out, or multiple-in-multiple-out (MIMO) systems.

Newer multiple access systems, for example, LTE, deliver faster data throughput than older technologies. Faster downlink rates, in turn, have sparked a greater demand for higher-bandwidth content, such as high-resolution graphics and video, for use on or with mobile devices. Therefore, demand for bandwidth on wireless communications systems continues to increase despite availability of higher data throughput over wireless interfaces, and this trend is likely to continue. However, wireless spectrum is a limited and regulated resource. Therefore, new approaches are needed in wireless communications to more fully utilize this limited resource and satisfy consumer demand.

BRIEF SUMMARY OF SOME EXAMPLES

The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled “DETAILED DESCRIPTION” one will understand how the features of this disclosure provide advantages that include improved communications between access points and stations in a wireless network.

Certain aspects of the present disclosure generally relate to techniques for allocating (or assigning) channels to multiple operators in the case of co-channel coexistence and interference to one or more other operators (e.g., incumbent operators).

Certain aspects of the present disclosure provide a method for wireless communication that may be performed, for example, by a network entity. The method generally includes evaluating, for different channel locations of a number of channels within an available spectrum, at least one of an amount of transmission limitation imposed to a group of devices due to incumbent protection, an amount of available bandwidth, or a maximum contiguous channel size. The method further includes assigning one of the channel locations to each of the number of channels, based on the evaluation.

Certain aspects of the present disclosure provide an apparatus for wireless communication. The apparatus generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to evaluate, for different channel locations of a number of channels within an available spectrum, at least one of an amount of transmission limitation imposed to a group of devices due to incumbent protection, an amount of available bandwidth, or a maximum contiguous channel size. The at least one processor is further configured to assign one of the channel locations to each of the number of channels, based on the evaluation.

Certain aspects of the present disclosure provide an apparatus for wireless communication. The apparatus generally includes means for evaluating, for different channel locations of a number of channels within an available spectrum, at least one of an amount of transmission limitation imposed to a group of devices due to incumbent protection, an amount of available bandwidth, or a maximum contiguous channel size. The apparatus further includes means for assigning one of the channel locations to each of the number of channels, based on the evaluation.

Certain aspects of the present disclosure provide a computer-readable medium having computer executable code stored thereon for wireless communication by an apparatus. The computer executable code generally includes code for evaluating, for different channel locations of a number of channels within an available spectrum, at least one of an amount of transmission limitation imposed to a group of devices due to incumbent protection, an amount of available bandwidth, or a maximum contiguous channel size. The computer executable code further includes code for assigning one of the channel locations to each of the number of channels, based on the evaluation.

Certain aspects of the present disclosure provide a method for wireless communications that may be performed, for example, by a network entity. The method generally includes determining one or more first channel locations in order to assign at least a first channel within available spectrum, wherein each first channel is associated with a group of devices sharing bandwidth within one or more networks. The method also includes participating in an exchange with at least a second network entity to share a first set of information associated with the first channel locations. The method further includes determining whether to modify at least a portion of the first set of information, based on the exchange.

Certain aspects of the present disclosure provide an apparatus for wireless communication. The apparatus generally includes at least one processor, and a memory coupled to the at least one processor. The at least one processor is configured to determining one or more first channel locations in order to assign at least a first channel within available spectrum, wherein each first channel is associated with a group of devices sharing bandwidth within one or more networks. The at least one processor is also configured to participate in an exchange with at least a second network entity to share a first set of information associated with the first channel locations. The at least one processor is further configured to determine whether to modify at least a portion of the first set of information, based on the exchange.

Certain aspects of the present disclosure provide an apparatus for wireless communication. The apparatus generally includes means for determining one or more first channel locations in order to assign at least a first channel within available spectrum, wherein each first channel is associated with a group of devices sharing bandwidth within one or more networks. The apparatus also includes means for participating in an exchange with at least a second network entity to share a first set of information associated with the first channel locations. The apparatus further includes means for determining whether to modify at least a portion of the first set of information, based on the exchange.

Certain aspects of the present disclosure provide a computer-readable medium having computer executable code stored thereon for wireless communication by an apparatus. The computer executable code generally includes code for determining one or more first channel locations in order to assign at least a first channel within available spectrum, wherein each first channel is associated with a group of devices sharing bandwidth within one or more networks. The computer executable code also includes code for participating in an exchange with at least a second network entity to share a first set of information associated with the first channel locations. The computer executable code further includes code for determining whether to modify at least a portion of the first set of information, based on the exchange.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.

FIG. 1 is a diagram illustrating an example of a network architecture, in accordance with certain aspects of the disclosure.

FIG. 2 is a diagram illustrating an example of an access network, in accordance with certain aspects of the disclosure.

FIG. 3 is a diagram illustrating an example of a DL frame structure in LTE, in accordance with certain aspects of the disclosure.

FIG. 4 is a diagram illustrating an example of an UL frame structure in LTE, in accordance with certain aspects of the disclosure.

FIG. 5 is a diagram illustrating an example of a radio protocol architecture for the user and control plane, in accordance with certain aspects of the disclosure.

FIG. 6 is a diagram illustrating an example of a base station (e.g., a evolved Node B or gNodeB) and user equipment in an access network, in accordance with certain aspects of the disclosure.

FIG. 7 is a block diagram showing aspects of an Authorized Shared Access (ASA) controller coupled to different wireless communication systems including one primary user and one secondary user, in accordance with certain aspects of the disclosure.

FIG. 8 is a block diagram showing aspects of an ASA controller coupled to different wireless communication systems including one primary user and multiple secondary users, in accordance with certain aspects of the disclosure.

FIG. 9 illustrates an example architecture of a spectrum sharing system, in accordance with certain aspects of the disclosure.

FIG. 10 illustrates an example of multiple General Authorized Access (GAA) networks with overlapping coverage, in accordance with certain aspects of the disclosure.

FIG. 11 is a flow diagram illustrating example operations that may be performed by a network entity to assign channel locations to orthogonal channels, in accordance with certain aspects of the present disclosure.

FIG. 12 illustrates an example of usable bandwidth within available spectrum, in accordance with certain aspects of the present disclosure.

FIG. 13 illustrates an example of building contiguous blocks, in accordance with certain aspects of the present disclosure.

FIG. 14 illustrates an example of contiguous blocks that satisfy a minimum bandwidth, in accordance with certain aspects of the present disclosure.

FIG. 15 illustrates an example of a bipartite graph used for matching channel locations to orthogonal channels, in accordance with certain aspects of the present disclosure.

FIG. 16 illustrates an example best matching of channel locations to orthogonal channels, in accordance with certain aspects of the present disclosure.

FIG. 17 is a flowchart for matching channel locations to orthogonal channels, in accordance with certain aspects of the present disclosure.

FIGS. 18 and 19 illustrate examples of matching channel locations to orthogonal channels, in accordance with certain aspects of the present disclosure.

FIG. 20 is a flowchart for determining channel location assignments, in accordance with certain aspects of the present disclosure.

FIG. 21 illustrates an example of multiple network entities covering the same geographic area, in accordance with certain aspects of the present disclosure.

FIG. 22 is a flow diagram illustrating example operations that may be performed by a network entity to perform conflict resolution, in accordance with certain aspects of the present disclosure.

To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation.

DETAILED DESCRIPTION

Aspects of the present disclosure provide techniques for mapping channels assigned to different technologies/sub-technologies/networks/operators to actual frequency locations for different groups of users and devices (e.g., citizen broadband service devices (CBSDs)) co-existing in the same spectrum, for example, the 3.5 GHz spectrum. The groups of users/devices occupying a given channel may be subject to interference limitations with respect to other wireless devices (e.g., incumbent operators).

As described below, a network entity (e.g., such as a base station, CBSD, spectrum access system (SAS), co-existence manager (CCM), etc.) may determine a number of (orthogonal) channels to assign to one or more groups of devices sharing bandwidth within a plurality of networks. In some cases, the number of (orthogonal) channels may be determined based in part on a number of networks in the plurality of networks that have overlapping coverage. The network entity may evaluate, for different channel locations of the (orthogonal) channels within an available spectrum, at least one of an amount of transmission limitation imposed to a group of devices due to incumbent protection, an amount of available bandwidth, or a maximum contiguous channel size. The network entity may assign one of the channel locations to each of the number of (orthogonal) channels, based on the evaluation. For example, the network entity may generate a frame including an indication of the assignment, and transmit the frame to the devices in the groups.

In one aspect, the network entity may perform the evaluation to reduce the likelihood that one or more of the groups in a network assigned to a channel location unfairly benefit from the assignment at the cost of other groups (assigned to that channel location or other channel locations) being limited. For example, the network entity may assign frequency (channel) locations in consideration of higher tiers (e.g., incumbent operators). In one aspect, the network entity may perform the evaluation to reduce the likelihood that network(s) assigned to channel locations unfairly benefit from the assignment in terms of an amount of bandwidth and/or contiguous frequency allocation at the cost of other networks assigned to other channel locations being limited.

As used herein, the term “network” may refer to a group of devices (e.g., CBSDs) that do not need orthogonalization (e.g., the devices can coexist), technologies (e.g., NR/5G, LTE, WiFi, etc.), systems, sub-technologies, operators, etc. The techniques described herein may be used for various wireless communication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio technology such as universal terrestrial radio access (UTRA), cdma2000, etc. UTRA includes wideband CDMA (WCDMA), time division synchronous CDMA (TD-SCDMA), and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as global system for mobile communications (GSM). An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are part of universal mobile telecommunication system (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A), in both frequency division duplex (FDD) and time division duplex (TDD), are new releases of UMTS that use E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). For clarity, certain aspects of the techniques are described below for LTE/LTE-Advanced, and LTE/LTE-Advanced terminology is used in much of the description below. LTE and LTE-A are referred to generally as LTE. But, the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies (e.g., NR).

A wireless communication network may include a number of base stations that can support communication for a number of wireless devices. Wireless devices may include user equipments (UEs). Some examples of UEs may include cellular phones, smart phones, personal digital assistants (PDAs), wireless modems, handheld devices, tablets, laptop computers, netbooks, smartbooks, ultrabooks, wearables (e.g., smart watch, smart bracelet, smart glasses, smart ring, smart clothing), etc.

System designs may support various time-frequency reference signals for the downlink and uplink to facilitate beamforming and other functions. A reference signal is a signal generated based on known data and may also be referred to as a pilot, preamble, training signal, sounding signal, and the like. A reference signal may be used by a receiver for various purposes such as channel estimation, coherent demodulation, channel quality measurement, signal strength measurement, and the like. MIMO systems using multiple antennas generally provide for coordination of sending of reference signals between antennas; however, LTE systems do not in general provide for coordination of sending of reference signals from multiple base stations or eNBs.

In some implementations, a system may use time division duplexing (TDD). For TDD, the downlink and uplink share the same frequency spectrum or channel, and downlink and uplink transmissions are sent on the same frequency spectrum. The downlink channel response may thus be correlated with the uplink channel response. Reciprocity may allow a downlink channel to be estimated based on transmissions sent via the uplink. These uplink transmissions may be reference signals or uplink control channels (which may be used as reference symbols after demodulation). The uplink transmissions may allow for estimation of a space-selective channel via multiple antennas.

In LTE implementations, orthogonal frequency division multiplexing (OFDM) is used for the downlink—that is, from a base station, access point or eNodeB (eNB) to a user terminal or UE. Use of OFDM meets the LTE requirement for spectrum flexibility and enables cost-efficient solutions for very wide carriers with high peak rates, and is a well-established technology. For example, OFDM is used in standards such as IEEE 802.11a/g, 802.16, High Performance Radio LAN-2 (HIPERLAN-2, wherein LAN stands for Local Area Network) standardized by the European Telecommunications Standards Institute (ETSI), Digital Video Broadcasting (DVB) published by the Joint Technical Committee of ETSI, and other standards.

Time frequency physical resource blocks (also denoted here in as resource blocks or “RBs” for brevity) may be defined in OFDM systems as groups of transport carriers (e.g., sub-carriers) or intervals that are assigned to transport data. The RBs are defined over a time and frequency period. Resource blocks are comprised of time-frequency resource elements (also denoted here in as resource elements or “REs” for brevity), which may be defined by indices of time and frequency in a slot. Additional details of LTE RBs and REs are described in the 3GPP specifications, such as, for example, 3GPP TS 36.211.

UMTS LTE supports scalable carrier bandwidths from 20 MHz down to 1.4 MHZ. In LTE, an RB is defined as 12 sub-carriers when the subcarrier bandwidth is 15 kHz, or 24 sub-carriers when the sub-carrier bandwidth is 7.5 kHz. In an exemplary implementation, in the time domain there is a defined radio frame that is 10 ms long and consists of 10 subframes of 1 millisecond (ms) each. Every subframe consists of 2 slots, where each slot is 0.5 ms. The subcarrier spacing in the frequency domain in this case is 15 kHz. Twelve of these subcarriers together (per slot) constitute an RB, so in this implementation one resource block is 180 kHz. Six Resource blocks fit in a carrier of 1.4 MHz and 100 resource blocks fit in a carrier of 20 MHz.

Various other aspects and features of the disclosure are further described below. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative and not limiting. Based on the teachings herein one of an ordinary level of skill in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. For example, a method may be implemented as part of a system, device, apparatus, and/or as instructions stored on a computer-readable medium for execution on a processor or computer. Furthermore, an aspect may comprise at least one element of a claim.

It is noted that while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as New Radio (NR), 5G, NR/5G, and later.

An Example Wireless Communications System

FIG. 1 is a diagram illustrating an LTE network architecture 100 in which aspects of the present disclosure may be practiced. For example, a central entity (not shown) may receive information regarding one or more groups of CBSDs (e.g., one or more groups of eNBs 106 and 108) within a plurality of networks. Such information, in one example, may include CBSD registration information, location information, transmit power information, antenna pattern, propagation model, etc. The central entity may create a coverage overlap graph based on the information, and determine which of the networks have overlapping coverage based on the coverage overlap graph. The central entity may assign orthogonal channels to the overlapping networks.

The central entity may evaluate, for different channel locations of the (orthogonal) channels, at least one of the amount of transmission limitation imposed to group(s) of devices associated with the respective channel location due to incumbent protection, an amount of available bandwidth, or a maximum contiguous channel size. The central entity may assign one of the channel locations to each (orthogonal) channel, based on the evaluation. The central entity may indicate, e.g., via RRC signaling (or some other indication) the channel location assignment for each (orthogonal) channel. In certain aspects, the role of the central entity may be performed by any node in the network 100, or by an independent entity. In one example, the central entity may be a spectrum access system (SAS). In one example, the central entity may be a co-existence manager (CXM).

The LTE network architecture 100 may be referred to as an Evolved Packet System (EPS) 100. The EPS 100 may include one or more user equipment (UE) 102, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 104, an Evolved Packet Core (EPC) 110, a Home Subscriber Server (HSS) 120, and an Operator's IP Services 122. The EPS can interconnect with other access networks, but for simplicity those entities/interfaces are not shown. Exemplary other access networks may include an IP Multimedia Subsystem (IMS) PDN, Internet PDN, Administrative PDN (e.g., Provisioning PDN), carrier-specific PDN, operator-specific PDN, and/or GPS PDN. As shown, the EPS provides packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit-switched services.

The E-UTRAN includes the evolved Node B (eNB) 106 and other eNBs 108. The eNB 106 provides user and control plane protocol terminations toward the UE 102. The eNB 106 may be connected to the other eNBs 108 via an X2 interface (e.g., backhaul). The eNB 106 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point, or some other suitable terminology. The eNB 106 may provide an access point to the EPC 110 for a UE 102. Examples of UEs 102 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a netbook, a smart book, an ultrabook, a drone, a robot, a sensor, a monitor, a meter, or any other similar functioning device. The UE 102 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

The eNB 106 is connected by an Si interface to the EPC 110. The EPC 110 includes a Mobility Management Entity (MME) 112, other MMES 114, a Serving Gateway 116, and a Packet Data Network (PDN) Gateway 118. The MME 112 is the control node that processes the signaling between the UE 102 and the EPC 110. Generally, the MME 112 provides bearer and connection management. All user IP packets are transferred through the Serving Gateway 116, which itself is connected to the PDN Gateway 118. The PDN Gateway 118 provides UE IP address allocation as well as other functions. The PDN Gateway 118 is connected to the Operator's IP Services 122. The Operator's IP Services 122 may include, for example, the Internet, the Intranet, an IP Multimedia Subsystem (IMS), and a PS (packet-switched) Streaming Service (PSS). In this manner, the UE102 may be coupled to the PDN through the LTE network.

FIG. 2 is a diagram illustrating an example of an access network 200 in an LTE network architecture in which aspects of the present disclosure may be practiced. For example, a central entity (not shown) may be configured to implement techniques for assigning (or allocating) channels to different groups of eNBs in the network 200 based on evaluating an amount of transmission limitation imposed for each pair of channel and group of eNBs assigned to the respective channel in the network 200, in accordance with certain aspects of the present disclosure.

In this example, the access network 200 is divided into a number of cellular regions (cells) 202. One or more lower power class eNBs 208 may have cellular regions 210 that overlap with one or more of the cells 202. A lower power class eNB 208 may be referred to as a remote radio head (RRH). The lower power class eNB 208 may be a femto cell (e.g., home eNB (HeNB)), pico cell, or micro cell. The macro eNBs 204 are each assigned to a respective cell 202 and are configured to provide an access point to the EPC 110 for all the UEs 206 in the cells 202. There is no centralized controller in this example of an access network 200, but a centralized controller may be used in alternative configurations. The eNBs 204 are responsible for all radio related functions including radio bearer control, admission control, mobility control, scheduling, security, and connectivity to the serving gateway 116. The network 200 may also include one or more relays (not shown). According to one application, a UE may serve as a relay.

The modulation and multiple access scheme employed by the access network 200 may vary depending on the particular telecommunications standard being deployed. In LTE applications, OFDM is used on the DL and SC-FDMA is used on the UL to support both frequency division duplexing (FDD) and time division duplexing (TDD). As those skilled in the art will readily appreciate from the detailed description to follow, the various concepts presented herein are well suited for LTE applications. However, these concepts may be readily extended to other telecommunication standards employing other modulation and multiple access techniques. By way of example, these concepts may be extended to Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. These concepts may also be extended to Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W-CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDMA. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.

The eNBs 204 may have multiple antennas supporting MIMO technology. The use of MIMO technology enables the eNBs 204 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data simultaneously on the same frequency. The data streams may be transmitted to a single UE 206 to increase the data rate or to multiple UEs 206 to increase the overall system capacity. This is achieved by spatially precoding each data stream (e.g., applying a scaling of an amplitude and a phase) and then transmitting each spatially precoded stream through multiple transmit antennas on the DL. The spatially precoded data streams arrive at the UE(s) 206 with different spatial signatures, which enables each of the UE(s) 206 to recover the one or more data streams destined for that UE 206. On the UL, each UE 206 transmits a spatially precoded data stream, which enables the eNB 204 to identify the source of each spatially precoded data stream.

Spatial multiplexing is generally used when channel conditions are good. When channel conditions are less favorable, beamforming may be used to focus the transmission energy in one or more directions. This may be achieved by spatially precoding the data for transmission through multiple antennas. To achieve good coverage at the edges of the cell, a single stream beamforming transmission may be used in combination with transmit diversity.

In the detailed description that follows, various aspects of an access network will be described with reference to a MIMO system supporting OFDM on the DL. OFDM is a spread-spectrum technique that modulates data over a number of subcarriers within an OFDM symbol. The subcarriers are spaced apart at precise frequencies. The spacing provides “orthogonality” that enables a receiver to recover the data from the subcarriers. In the time domain, a guard interval (e.g., cyclic prefix) may be added to each OFDM symbol to combat inter-OFDM-symbol interference. The UL may use SC-FDMA in the form of a DFT-spread OFDM signal to compensate for high peak-to-average power ratio (PAPR).

FIG. 3 is a diagram 300 illustrating an example of a DL frame structure in LTE. A frame (10 ms) may be divided into 10 equally sized sub-frames with indices of 0 through 9. Each sub-frame may include two consecutive time slots. A resource grid may be used to represent two time slots, each time slot including a resource block. The resource grid is divided into multiple resource elements. In LTE, a resource block contains 12 consecutive subcarriers in the frequency domain and, for a normal cyclic prefix in each OFDM symbol, 7 consecutive OFDM symbols in the time domain, or 84 resource elements. For an extended cyclic prefix, a resource block contains 6 consecutive OFDM symbols in the time domain and has 72 resource elements. Some of the resource elements, as indicated as R 302, R 304, include DL reference signals (DL-RS). The DL-RS include Cell-specific RS (CRS) (also sometimes called common RS) 302 and UE-specific RS (UE-RS) 304. UE-RS 304 are transmitted only on the resource blocks upon which the corresponding physical DL shared channel (PDSCH) is mapped. The number of bits carried by each resource element depends on the modulation scheme. Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate for the UE.

In LTE, an eNB may send a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for each cell in the eNB. The primary and secondary synchronization signals may be sent in symbol periods 6 and 5, respectively, in each of subframes 0 and 5 of each radio frame with the normal cyclic prefix (CP). The synchronization signals may be used by UEs for cell detection and acquisition. The eNB may send a Physical Broadcast Channel (PBCH) in symbol periods 0 to 3 in slot 1 of subframe 0. The PBCH may carry certain system information.

The eNB may send a Physical Control Format Indicator Channel (PCFICH) in the first symbol period of each subframe. The PCFICH may convey the number of symbol periods (M) used for control channels, where M may be equal to 1, 2 or 3 and may change from subframe to subframe. M may also be equal to 4 for a small system bandwidth, e.g., with less than 10 resource blocks. The eNB may send a Physical HARQ Indicator Channel (PHICH) and a Physical Downlink Control Channel (PDCCH) in the first M symbol periods of each subframe. The PHICH may carry information to support hybrid automatic repeat request (HARQ). The PDCCH may carry information on resource allocation for UEs and control information for downlink channels. The eNB may send a Physical Downlink Shared Channel (PDSCH) in the remaining symbol periods of each subframe. The PDSCH may carry data for UEs scheduled for data transmission on the downlink.

The eNB may send the PSS, SSS, and PBCH in the center 1.8 MHz of the system bandwidth used by the eNB. The eNB may send the PCFICH and PHICH across the entire system bandwidth in each symbol period in which these channels are sent. The eNB may send the PDCCH to groups of UEs in certain portions of the system bandwidth. The eNB may send the PDSCH to specific UEs in specific portions of the system bandwidth. The eNB may send the PSS, SSS, PBCH, PCFICH, and PHICH in a broadcast manner to all UEs, may send the PDCCH in a unicast manner to specific UEs, and may also send the PDSCH in a unicast manner to specific UEs.

A number of resource elements may be available in each symbol period. Each resource element (RE) may cover one subcarrier in one symbol period and may be used to send one modulation symbol, which may be a real or complex value. Resource elements not used for a reference signal in each symbol period may be arranged into resource element groups (REGs). Each REG may include four resource elements in one symbol period. The PCFICH may occupy four REGs, which may be spaced approximately equally across frequency, in symbol period 0. The PHICH may occupy three REGs, which may be spread across frequency, in one or more configurable symbol periods. For example, the three REGs for the PHICH may all belong in symbol period 0 or may be spread in symbol periods 0, 1, and 2. The PDCCH may occupy 9, 18, 36, or 72 REGs, which may be selected from the available REGs, in the first M symbol periods, for example. Only certain combinations of REGs may be allowed for the PDCCH. In aspects of the present methods and apparatus, a subframe may include more than one PDCCH.

A UE may know the specific REGs used for the PHICH and the PCFICH. The UE may search different combinations of REGs for the PDCCH. The number of combinations to search is typically less than the number of allowed combinations for the PDCCH. An eNB may send the PDCCH to the UE in any of the combinations that the UE will search.

FIG. 4 is a diagram 400 illustrating an example of an UL frame structure in LTE. The available resource blocks for the UL may be partitioned into a data section and a control section. The control section may be formed at the two edges of the system bandwidth and may have a configurable size. The resource blocks in the control section may be assigned to UEs for transmission of control information. The data section may include all resource blocks not included in the control section. The UL frame structure results in the data section including contiguous subcarriers, which may allow a single UE to be assigned all of the contiguous subcarriers in the data section.

A UE may be assigned resource blocks 410 a, 410 b in the control section to transmit control information to an eNB. The UE may also be assigned resource blocks 420 a, 420 b in the data section to transmit data to the eNB. The UE may transmit control information in a physical UL control channel (PUCCH) on the assigned resource blocks in the control section. The UE may transmit only data or both data and control information in a physical UL shared channel (PUSCH) on the assigned resource blocks in the data section. A UL transmission may span both slots of a subframe and may hop across frequency.

A set of resource blocks may be used to perform initial system access and achieve UL synchronization in a physical random access channel (PRACH) 430. The PRACH 430 carries a random sequence and cannot carry any UL data/signaling. Each random access preamble occupies a bandwidth corresponding to six consecutive resource blocks. The starting frequency is specified by the network. That is, the transmission of the random access preamble is restricted to certain time and frequency resources. There is no frequency hopping for the PRACH. The PRACH attempt is carried in a single subframe (1 ms) or in a sequence of few contiguous subframes and a UE can make only a single PRACH attempt per frame (10 ms).

FIG. 5 is a diagram 500 illustrating an example of a radio protocol architecture for the user and control planes in LTE. The radio protocol architecture for the UE and the eNB is shown with three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various physical layer signal processing functions. The L1 layer will be referred to herein as the physical layer 506. Layer 2 (L2 layer) 508 is above the physical layer 506 and is responsible for the link between the UE and eNB over the physical layer 506.

In the user plane, the L2 layer 508 includes a media access control (MAC) sublayer 510, a radio link control (RLC) sublayer 512, and a packet data convergence protocol (PDCP) 514 sublayer, which are terminated at the eNB on the network side. Although not shown, the UE may have several upper layers above the L2 layer 508 including a network layer (e.g., IP layer) that is terminated at the PDN gateway 118 on the network side, and an application layer that is terminated at the other end of the connection (e.g., far end UE, server, etc.).

The PDCP sublayer 514 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 514 also provides header compression for upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and handover support for UEs between eNBs. The RLC sublayer 512 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ). The MAC sublayer 510 provides multiplexing between logical and transport channels. The MAC sublayer 510 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 510 is also responsible for HARQ operations.

In the control plane, the radio protocol architecture for the UE and eNB is substantially the same for the physical layer 506 and the L2 layer 508 with the exception that there is no header compression function for the control plane. The control plane also includes a radio resource control (RRC) sublayer 516 in Layer 3 (L3 layer). The RRC sublayer 516 is responsible for obtaining radio resources (i.e., radio bearers) and for configuring the lower layers using RRC signaling between the eNB and the UE.

FIG. 6 is a block diagram of an eNB 610 in communication with a UE 650 in an access network, in which aspects of the present disclosure may be practiced. For example, a central entity (not shown) may evaluate an amount of transmission limitation imposed on each pair of channel and group of eNBs (e.g., eNBs 610) assigned to the respective channel. The central entity may assign a channel to each group of eNBs based on the evaluation. It may be noted that the central entity may be implemented by eNB 610 or UE 650.

In the DL, upper layer packets from the core network are provided to a controller/processor 675. The controller/processor 675 implements the functionality of the L2 layer, for example. In the DL, the controller/processor 675 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the UE 650 based on various priority metrics. The controller/processor 675 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE 650.

The TX processor 616 implements various signal processing functions for the L1 layer (i.e., physical layer), for example. The signal processing functions includes coding and interleaving to facilitate forward error correction (FEC) at the UE 650 and mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then split into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 674 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 650. Each spatial stream is then provided to a different antenna 620 via a separate transmitter 618TX. Each transmitter 618TX modulates an RF carrier with a respective spatial stream for transmission.

At the UE 650, each receiver 654RX receives a signal through its respective antenna 652. Each receiver 654RX recovers information modulated onto an RF carrier and provides the information to the receiver (RX) processor 656. The RX processor 656 implements various signal processing functions of the L1 layer, for example. The RX processor 656 performs spatial processing on the information to recover any spatial streams destined for the UE 650. If multiple spatial streams are destined for the UE 650, they may be combined by the RX processor 656 into a single OFDM symbol stream. The RX processor 656 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, is recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 610. These soft decisions may be based on channel estimates computed by the channel estimator 658. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 610 on the physical channel. The data and control signals are then provided to the controller/processor 659.

The controller/processor 659 implements the L2 layer, for example. The controller/processor 659 can be associated with a memory 660 that stores program codes and data. The memory 660 may be referred to as a computer-readable medium. In the UL, the controller/processor 659 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packets are then provided to a data sink 662, which represents all the protocol layers above the L2 layer. Various control signals may also be provided to the data sink 662 for L3 processing. The controller/processor 659 is also responsible for error detection using an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support HARQ operations.

In the UL, a data source 667 is used to provide upper layer packets to the controller/processor 659, for example. The data source 667 represents all protocol layers above the L2 layer, for example. Similar to the functionality described in connection with the DL transmission by the eNB 610, the controller/processor 659 implements the L2 layer for the user plane and the control plane by providing header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations by the eNB 610, for example. The controller/processor 659 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the eNB 610, for example.

Channel estimates derived by a channel estimator 658 from a reference signal or feedback transmitted by the eNB 610 may be used by the TX processor 668 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 668 are provided to different antenna 652 via separate transmitters 654TX. Each transmitter 654TX modulates an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the eNB 610 in a manner similar to that described in connection with the receiver function at the UE 650. Each receiver 618RX receives a signal through its respective antenna 620. Each receiver 618RX recovers information modulated onto an RF carrier and provides the information to a RX processor 670. The RX processor 670 may implement the L1 layer, for example.

The controller/processor 675 implements the L2 layer, for example. The controller/processor 675 can be associated with a memory 676 that stores program codes and data. The memory 676 may be referred to as a computer-readable medium. In the UL, the control/processor 675 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 650. Upper layer packets from the controller/processor 675 may be provided to the core network. The controller/processor 675 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations. The controllers/processors 675, 659 may direct the operations at the eNB 610 and the UE 650, respectively.

The controller/processor 675 and/or other processors, components and/or modules at the eNB 610 or the controller/processor 659 and/or other processors, components and/or modules at the UE 650 may perform or direct operations, for example, operations 1100 in FIG. 11, operations 1700 in FIG. 17, operations 2000 in FIG. 20, operations 2200 in FIG. 22, and/or other processes for the techniques described herein for assigning channels to groups of devices sharing bandwidth in presence of incumbent devices. In certain aspects, one or more of any of the components shown in FIG. 6 may be employed to perform example operations 1100 in FIG. 11, operations 1700 in FIG. 17, operations 2000 in FIG. 20, operations 2200 in FIG. 22, and/or other processes for the techniques described herein. The memories 660 and 676 may store data and program codes for the UE 650 and eNB 610 respectively, accessible and executable by one or more other components of the UE 650 and the eNB 610.

Example Authorized Shared Access for 3.5 GHz CBRS Band

Due to the explosive growth in mobile broadband traffic and its strain on limited spectrum resources, the Federal Communications Commission (FCC) has adopted rules to allow commercial shared use of 150 MHz of spectrum in the 3550-3700 MHz (3.5 GHz) band for licensed and unlicensed use of the 3.5 GHz band for a wide variety of services.

Citizens Broadband Radio service (CBRS) is a tiered commercial radio service with a 3.5 GHz band in the U.S. A Spectrum Access System (SAS) may allocate channels within and across tiers. These tiers can include, in order of priority, (1) incumbent licensees (operators); (2) Priority Access licensees (PALs); and (3) General Authorized Access (GAA) operators.

Authorized shared access (ASA) allocates, to a secondary user(s), portions of spectrum that are not continuously used by an incumbent system(s). The incumbent system may be referred to as an incumbent licensee, Tier 1 operator, primary licensee, or a primary user that is given a primary license for a band of frequencies. The incumbent system may not use the entire frequency band in all locations and/or at all times. The secondary user may be referred to as a secondary licensee or a secondary network. Aspects of the present disclosure are directed to an ASA implementation. Still, the ASA technology is not limited to the illustrated configurations as other configurations are also contemplated. The ASA spectrum refers to portion(s) of a spectrum that is not used by a primary user and has been licensed for use by a secondary user, such as an ASA operator. ASA spectrum availability may be specified by location, frequency, and/or time. It should be noted that the authorized shared access may also be referred to as licensed shared access (LSA).

A PAL is an authorization to use a channel (e.g., an unpaired 10 MHz channel) in the 3.5 GHz range in a geographic service area for a period (e.g., 3 years). The PAL geographic service area may be census tracts, which typically align with the borders of political boundaries such as cities or counties. PAL licensees can aggregate up to four PA channels in any census tract at any given time, and may obtain licenses in any available census tract. PALs may provide interference protection for Tier 1 incumbent licensees and accept interference from them; however, PALs may be entitled to interference protection from GAA operators.

The third tier, GAA, permits access to bandwidth (e.g., 80 MHz) of the 3.5 GHz band that is not assigned to a higher tier (i.e., incumbent licensees or PALs). GAA may be licensed “by rule,” meaning that entities that qualify to be FCC licensees may use FCC-authorized telecommunications equipment in the GAA band without having to obtain an individual spectrum license. GAA operators may receive no interference protection from PALs or Tier 1 operators, and may accept interference from them.

To facilitate the complex CBRS spectrum sharing process, a Spectrum Access System (“SAS”), which may be a highly automated frequency coordinator, can be used to assign frequencies in the 3.5 GHz band. The SAS can also authorize and manage use of the CBRS spectrum, protect higher tier operations from interference, and maximize frequency capacity for all CBRS operators.

Example ASA Architecture

In one configuration, as shown in FIG. 7, an ASA architecture 700 includes an ASA controller 702 coupled to an incumbent network controller 712 of a primary user and an ASA network manager 714 of an ASA network. The primary user may be a primary ASA licensee and the ASA network may be a secondary user.

In one configuration, the incumbent network controller is a network entity operated by the primary user that controls and/or manages the network operating in the ASA spectrum. Furthermore, the ASA network manager may be a network entity operated by the ASA network operator that controls and/or manages an associated network, including but not limited to the devices operating in the ASA spectrum. Additionally, the secondary licensee may be a wireless network operator that has obtained an ASA license to use the ASA spectrum. Furthermore, in one configuration, the ASA controller is a network entity that receives information from the incumbent network controller on the available ASA spectrum that may be used by an ASA network. The ASA controller may also transmit control information to the ASA network manager to notify the ASA network manager of the available ASA spectrum.

In one sample configuration, the incumbent network controller 712 is aware of the use of the ASA spectrum by the primary user at specified times and/or locations. The incumbent network controller 712 may provide information to the ASA controller 702 for the incumbent usage of the ASA spectrum. There are several methods that the incumbent network controller 712 can use to provide this information to the ASA controller 702. In one configuration, the incumbent network controller 712 provides a set of exclusion zones and/or exclusion times to the ASA controller 702. In another configuration, the incumbent network controller 712 specifies a threshold for allowed interference at a set of locations. The threshold for allowed interference may be referred to as incumbent protection information. In this configuration, the incumbent protection information is transmitted to the ASA controller 702 over an ASA-1 interface 716. Incumbent protection information may be stored by the ASA controller 702 in a database 706.

The ASA-1 interface refers to the interface between the primary user and the ASA controller. The ASA-2 interface refers to the interface between the ASA controller and the ASA network management system. Moreover, the ASA-3 interface refers to the interface between the ASA network manager and the ASA network elements. Furthermore, geographic sharing refers to an ASA sharing model in which the ASA network can operate throughout a geographic region for an extended period of time. The network is not permitted to operate in regions specified by exclusion zones.

The ASA controller 702 uses the information from the incumbent network controller 712 to determine the ASA spectrum that may be used by the ASA network. That is, the ASA controller 702 determines the ASA spectrum that may be used for a specific time and/or a specific location based on rules specified in a rules database 708. The rules database 708 may be accessed by an ASA processor 704 and stores the regulatory rules that are set by local regulations. These rules may not be modified by the ASA-1 or the ASA-2 interfaces, and may be updated by the individual or organization that manages the ASA controller 702. The available ASA spectrum, as calculated by the rules in the rules database 708, may be stored in the ASA spectrum availability database 710.

The ASA controller 702 may send information to the ASA network manager 714 on the available ASA spectrum via an ASA-2 interface 718, based on the spectrum availability database. The ASA network manager 714 may know or determine the geographic location of base stations under its control and also information about the transmission characteristics of these base stations, such as transmit power and/or supported frequencies of operation. The ASA network manager 714 may query the ASA controller 702 to discover the available ASA spectrum in a given location or a geographic region. Also, the ASA controller 702 may notify the ASA network manager 714 of any updates to the ASA spectrum availability in real-time. This allows the ASA controller 702 to notify the ASA network manager 714 if the ASA spectrum is no longer available, so that the ASA network can stop using that spectrum and the incumbent network controller 712 can obtain exclusive access to the ASA spectrum in real time.

The ASA network manager 714 may be embedded in a standard network element, depending on the core network technology. For example, if the ASA network is a new radio (NR or NR 5G) or long term evolution (LTE) network, the ASA network manager can be embedded in an operations, administration, and maintenance (OAM) server.

In FIG. 7, an incumbent network controller and a single ASA network manager are illustrated as being coupled to the ASA controller. It is also possible for multiple ASA networks (e.g., ASA network A, ASA network B and ASA network C) to be connected to an ASA controller 802, as in a system 800 shown in FIG. 8. ASA network A includes an ASA network A manager 814 coupled to the ASA controller 802, ASA network B includes an ASA network B manager 820 coupled to the ASA controller 802, and ASA network C includes an ASA network C manager 822 coupled to the ASA controller 802.

In this example, the multiple ASA networks may share the same ASA spectrum. The ASA spectrum may be shared via various implementations. In one example, the ASA spectrum is shared for a given region, so that each network is restricted to a subband within the ASA spectrum. In another example, the ASA networks share the ASA spectrum by using timing synchronization and scheduling the channel access of the different networks.

The system 800 may further include an incumbent network controller 812 of a primary user communicating with the ASA controller 802 via an ASA-1 interface 816, to provide incumbent protection information for a database 806. The ASA controller 802 may include a processor 804 coupled to a rules database 808 and ASA spectrum availability database 810. The ASA controller 802 may communicate with the ASA network managers 814, 820 and 822 via an ASA-2 interface 818. The ASA networks A, B, C may be secondary users.

The ASA network manager(s) may interact with various network elements, such as eNodeBs, to achieve the desired spectrum use control. The interaction may be implemented via the ASA-3 interface between eNodeBs in the RAN and an ASA network manager node embedded in an operations, administration, and maintenance server. The RAN may be coupled to a core network. An ASA controller may be coupled to the operations, administration, and maintenance server via an ASA-2 interface and to a network controller of a primary user via an ASA-1 interface.

In some cases, multiple incumbent network controllers are specified for the same ASA spectrum. That is, a single incumbent network controller may provide information about incumbent protection for a given ASA frequency band. Therefore, the architecture may be limited to a single incumbent network controller. However, it is noted that multiple incumbent network controllers may be supported. Still, it may be desirable to limit the network to a single incumbent network controller.

Spectrum Sharing systems, such as SAS, allow for radio resources (e.g., operating frequency, transmission power limits, and geographic areas) to be assigned dynamically among multiple users and service providers while providing some degree of protection of other users/service providers and incumbent users that potentially have higher priority (e.g., fixed satellite systems, WISPs, and government/military systems).

FIG. 9 illustrates an example architecture 900 of a spectrum sharing system. As illustrated, the spectrum sharing system may comprise one or more Spectrum Access Servers (SASs) (e.g., an ASA Controller) which are the entities that accept requests for radio resources from one or more Citizens Broadband Radio Service Devices (CBSDs), resolve conflicts or over-constraints in those requests, and grant the use of resources to radio access services.

When competing users and radio systems, (e.g., CBSDs) vie for radio resources, there is also a challenge of protecting these radio resources from each other based on restrictions due to the radio access technologies that are being used and a number of operational aspects for those radio access technologies. For example, some users/system operators may be able to coexist in the same or neighboring radio channels based on their use of the same (or compatible) radio technologies, compatible Self Organizing Network technologies, synchronized timing, common operational parameters (e.g., TDD slot structures, common radio silence intervals, etc.), and access to the same Core Networks for seamless mobility, etc.

Example Channel Mapping in Shared Spectrum in the Presence of Higher-Tier Users

As noted above, in a multi-tier commercial radio service (e.g., such as citizens broadband radio service (CBRS)), different tiers of operators may be able to share portions of the same spectrum. In one reference example, different general authorized access (GAA) networks or technologies may be able to share different portions of the same bandwidth (e.g., one GAA network may be allocated 20 MHz and another GAA network may be allocated 20 MHz).

In some cases, however, the GAA spectrum may not be completely clean in terms of incumbent limitations. That is, while using GAA spectrum, one or more GAA networks may be in the presence of a device belonging to a higher priority tier (e.g., such as an incumbent tier, PAL tier, etc.) and may have to respect the interference limit at the higher priority tier. In one case, for example, there may be a limit of −129 dBm/MHz for aggregated interference at fixed satellite services (FSSs), which is one type of incumbent operator. Thus, in some cases, a given GAA network, in order to respect a higher priority tier, may be subject to more transmission limitations (e.g., transmission power limitations) compared to another co-existing GAA network. In some cases, however, having different interference limits for different groups of operators (e.g., GAA networks) can impact the fairness for intra-GAA channel assignment.

For example, with reference to FIG. 10, assume there are three GAA networks (e.g., GAA network 1, GAA network 2, and GAA network 3), each including a group of CBSDs. In this example, there may be an intra-GAA coexistence between these three GAA networks. At the same time, however, these networks may not be the same from an incumbent protection point of view. That is, one or more of the CBSDs in a given GAA network (e.g., GAA network 1) may have a greater transmission limitation (due to incumbent/PAL protection) than another GAA network (e.g., GAA network 2 and/or GAA network 3). In such cases, a network entity 1002 (e.g., SAS/CxM) may be configured to allocate bandwidth to each of the networks from an intra-GAA coexistence point of view. For example, the network entity 1002 may assign orthogonal channels to overlapping networks. Referring to the example in FIG. 10, GAA network 1 overlaps with GAA network 2, and GAA network 2 overlaps with GAA network 3. The network entity 1002, therefore, may assign an orthogonal channel for use by GAA networks 1 and 3, and another orthogonal channel for use by GAA network 2. To do so, the network entity 1002 may create a coverage overlap graph based on each CBSD's registration information, which may include information regarding the CBSD's location, transmit power, antenna pattern, propagation model, etc. Two networks may be connected in the graph if they have overlapping coverage. Once created, the network entity 1002 may separate different connected sets (disjoint subgraphs), color (label, shade, etc.) each separated connected set a different color, and assign equal bandwidth to each color. As shown in FIG. 10, for example, the network entity 1002 may assign equal bandwidth to the orthogonal channel (e.g., first color) associated with networks 1 and 3, and the orthogonal channel (e.g., second color) associated with network 2.

However, while the network entity 1002 may assign equal bandwidth to each orthogonal channel, there may be other factors that affect the fairness of the channel assignment. These factors may include, but are not limited to, higher tier consideration, satisfying minimum bandwidth requirements contiguous frequency allocation, quantization impacts, etc. To ensure an efficient and fair matching, the network entity 1002 may consider one or more of the above factors.

For example, in the case of intra-GAA coexistence constraints, CBSDs that have the same color (or orthogonal channel) may have to have the same primary channel (e.g., in order to respect the intra-GAA coexistence that is based on the overlapping network coverage). In addition, there may be fairness and efficiency implications for different channel location assignments with respect to incumbent/PAL limitations. In other words, different channels may experience different limitations from incumbent/PAL protection point of view. Thus, in some aspects, the network entity 1002 may have to blacklist some part of the spectrum for GAA primary channel (e.g., due to severe EIRP limitations). Further, in some cases, the network entity 1002 may have to choose channel locations that allow for as much of a contiguous channel as possible. For example, a single contiguous 20 MHz channel may be more useful than four non-adjacent 5 MHz channels. There may also be quantization impacts that should be considered. For example, assuming the primary channel bandwidth is a multiple of 5 MHz channel units, the network entity 1002 may have to assign channel locations that may not allow for 5 MHz channel units (e.g., allocating three orthogonal channels among 80 MHz). Further yet, the network entity 1002 may have to assign channel locations to orthogonal channels in very congested areas. For example, there may be a large number of orthogonal channels that have small primary channel bandwidths (e.g., below 5 MHz, such as the case where 40 MHz is available and 10 channel locations are needed).

Aspects presented herein provide techniques that can be used (e.g., by a network entity, a spectrum access system (SAS), a coexistence manager (CxM), or a domain proxy (DP)) to account for one or more of the above factors (or any combination of the above factors) when mapping frequency locations to orthogonal channels used by different networks that share spectrum.

FIG. 11 illustrates example operations 1100 for assigning channels to multiple operators sharing bandwidth, in accordance with certain aspects of the present disclosure. According to certain aspects, example operations 1100 may be performed, for example, by a network entity such as an eNB (e.g., eNB 106) which may be CBSD, a SAS (e.g., one or more of the SASs illustrated in FIG. 9), co-existence manager (CCM), or other network entity operating between SAS and CBSD (e.g., EMS illustrated in FIG. 9 or ASA controller 702 or 802 illustrated in FIGS. 7 and 8, respectively).

Operations 1100 begin at 1102, where the network entity evaluates, for different channel locations of a number of orthogonal channels within an available spectrum, at least one of an amount of transmission limitation imposed to a group of devices due to incumbent protection, an amount of available bandwidth, or a maximum contiguous channel size. In some aspects, the network entity may determine the number of (orthogonal) channels to assign to one or more groups of devices sharing bandwidth within a plurality of networks, based in part on a number of networks in the plurality of networks that have overlapping coverage. For example, the network entity may determine the number of networks that have overlapping coverage based on a coverage map generated in part based on each CBSD's registration information.

At 1104, the network entity assigns one of the channel locations to each of the number of orthogonal channels, based on the evaluation. In one aspect, the assigning is such that the amount of available bandwidth at the channel location of each orthogonal channel is above a threshold bandwidth. Additionally, or alternatively, in one aspect, the assigning is such that the amount of transmission limitation imposed to a group of devices at each channel location is below a threshold. In some aspects, the network entity may generate one or more frames, each including an indication of the assigned channel locations, and transmit the frames to the devices in the different groups of devices.

In one aspect, the wireless devices in the different groups may include at least one of a base station or a CBSD. In one aspect, the wireless devices in the different groups may belong to at least one tier of a multi-tier commercial radio service (e.g., CBRS), and the incumbent devices may belong to at least another tier of a multi-tier commercial radio service. For example, in one implementation, one (lower) tier may include GAA operators and the other (higher) tier may include PALs. In one implementation, one (lower) tier may include PALs, and the other (higher) tier may include incumbent operators. In one implementation, one (lower) tier may include GAA operators, and the other (higher) tier may include joint incumbent and PAL operators.

In some aspects, after the network entity determines the number of (orthogonal) channels to assign, the network entity may determine a number of available channel locations within a spectrum that are available for assigning to the (orthogonal) channels. In one aspect, the network entity may determine that at least one channel location is unusable for the assignment, based on the evaluation, and remove the determined unusable channel locations from the assignment of channel locations to each of the number of (orthogonal) channels.

Assume, for example, that for a given geographical area (or connected set), C colors (or orthogonal channels) are determined. In this example, each CBSD may be mapped to a color cϵ{1, 2, . . . , C}. Assuming the available spectrum is divided into channel units of 5 MHz, the channel units may be denoted by hϵ{1, 2, . . . , H_(u)}. Further assume that there are P protected points (incumbent/PAL) that are potentially impacted by GAA CBSDs in the given connected set under consideration. Let Q_(p) denote the interference quota (threshold limit) for protected point p=1, 2, . . . , P. Then, for each color cϵ{1, 2, . . . , C} and each channel unit hϵ{1, 2, . . . , H_(u)}, the network entity may define a limitation metric m_(c,h) (Equation 1) as the overall transmit power limit imposed on CBSDs with color c if it is assigned to channel unit h:

$\begin{matrix} {m_{c,h} = {\max\limits_{{p = 1},2,{\ldots P}}\left\{ {\left( {\Sigma_{n \in {{CBSDs}{with}{color}c}}I_{h,n,p}^{\max}} \right)_{dBm} - \left( Q_{p} \right)_{dBm}} \right\}}} & (1) \end{matrix}$

where (Σ_(n∈CBSDs with color c)I_(h,n,p) ^(max))_(dBm) is the sum of interference at the protected point p as a result of transmission of CBSDs with color c in channel unit h at their max EIRP. For a given protected point p, m_(c,h) is equal to the average power reduction across all CBSDs with color c in order to satisfy the aggregated interference constraint for that protected point in some power allocation methods.

In some aspects, the network entity may blacklist unusable channel units based in part on the transmission power limit m_(c,h). For example, in one aspect, the network entity may determine that the at least one channel location is unusable if the amount of transmission limitation imposed to the group of devices associated with the channel location is greater than a threshold.

For example, let

$m_{h} = {\min\limits_{c \in {\{{1,2,\ldots,C}\}}}{m_{c,h}.}}$

For a given channel unit h, m_(h) is the smallest limitation metric across all colors cϵ{1, 2, . . . , C}. If m_(h) is greater than a threshold (e.g., 20 dB), then the network entity may blacklist channel unit h. The blacklisted channel unit may not be usable for any color (e.g., orthogonal channel), as the aggregated interference from CBSDs with that color is at least (e.g., 20 dB) larger than the interference limit. All other remaining channel units U_(h) may be qualified as usable (e.g., U_(h) ⊆{1, 2, . . . , H_(u)}). Each member of U_(h) may be usable for at least one color. Assuming the smallest bandwidth unit is 5 MHz, the total usable bandwidth may be 5*|U_(h)| (MHz). FIG. 12 shows one example of determining the usable bandwidth within an available spectrum. In the depicted example, the total number of channel units H_(u)=10 (e.g., 50 MHz BW). Three channel units, h=2, 4 and 8, are blacklisted. Thus, in this example, U_(h)={1,3,5,6,7,9,10}, |U_(h)|=7.

In one aspect, after the network entity determines the amount of usable bandwidth that is available for assigning channel locations to the colors (e.g., orthogonal channels), the network entity may evaluate each channel location to determine the maximum available contiguous channel block size. As noted above, contiguous primary channels are generally preferred over multiple non-contiguous channels. However, depending on the available bandwidth, number of colors, and blacklisting, assigning large contiguous channel blocks may not always be feasible.

Consider, for example, a channel block as i contiguous channel units. For example, i=4, 3, 2, 1 corresponds to 20, 15, 10, 5 MHz contiguous channel blocks, respectively. In some cases, the largest possible i for C colors may be defined as

$\left\lfloor \frac{❘U_{h}❘}{C} \right\rfloor,$

which may not always be possible.

Accordingly, aspects presented herein provide techniques that the network entity can use to build the largest contiguous channel block size for a given channel location. For example, for a given i, let H_(bi) denote the maximum number of non-overlapping channel blocks (consisting of I contiguous channel units) from usable channel units U_(h). H_(bi) may depend on |U_(h)| as well as the contiguousness of U_(h) (e.g., how many contiguous pieces does U_(h) have, etc.). For each i, the network entity may start from the smallest member of U_(h) and find the next i contiguous channel units. The network entity may continue unto no other channel block can be built. FIG. 13 illustrates an example of building contiguous channel blocks for i=2 and i=3. As shown, for i=2, two channel blocks of 10 MHz from U_(h) can be built (e.g., H_(b) ₂ =2). For i=1, one channel block of 15 MHz can be built (e.g., H_(b) ₃ =1).

In some aspects, the network entity may assign the channel locations such that the amount of available bandwidth at the channel location of each orthogonal channel is above a threshold bandwidth (e.g., BW_(min)). For example, the minimum contiguous primary channel that each CBSD may use may be denoted as BW_(min) (e.g., 10 MHz or 5 MHz, or any multiple of 5 MHz or other minimum bandwidth). Having a BW_(min) may mean that, in some cases, CBSDs may be willing to tolerate more interference in order to get at least BW_(min) MHz contiguous primary channel. Let

$r = \frac{{BW}_{\min}}{5}$

denote the minimum number of contiguous channel units that have to be allocated a primary channel. In this case, H_(b) _(r) is the maximum number of channel blocks (each with r contiguous channel units) belonging to usable channel units U_(h) as described above. For example, if BW_(min)=10 MHz→r=2→H_(b) ₂ =2. FIG. 14 depicts an example of a spectrum with two channel blocks that satisfy H_(b) ₂ =2.

In some aspects, however, if the number of colors is too large (e.g., above a threshold), the network entity may be forced to allow some primary channels to be smaller than BW_(min). For example, in one aspect, the network entity may decrease the number of colors C by increasing the coverage and interference thresholds, which may result in a decreasing number of edges in the coverage graph. In one aspect, the network entity may increase the number of usable channels U_(h) by increasing the blacklisting threshold. Thus, if the network entity determines that C>H_(b) _(r) , the network entity may be forced to allow the primary channel to become smaller than BW_(min). In order to ensure primary channel to become equal or larger than BW_(min) for all CBSDs, the network entity may incrementally increase the coverage and/or interference thresholds as well as the blacklisting threshold (e.g., in steps of 3 dB). The network entity may then continue to do the coloring and blacklisting until C≤H_(b) _(r) .

According to certain aspects, within the different assignments of channel locations to orthogonal channels, the network entity may perform the evaluating of the above factors for each pair of channel location and group of wireless devices assigned to the given orthogonal channel. Put differently, given a set of colors {1, 2, . . . , C} and a set of channel blocks {1, 2, . . . , H_(b)}, the network entity may determine the best “matching” for the colors (orthogonal channels). In one aspect, the network entity may define a cost metric M_(c,h) _(b) (Equation 2) for each color c∈{1, 2, . . . , C} and each channel block h_(b) ∈{1, 2, . . . , H_(b)} using m_(c,h) (e.g., Equation 1), as

$\begin{matrix} {M_{c,h_{b}} = {\max\limits_{h \in {{channel}{block}h_{b}}}m_{c,h}}} & (2) \end{matrix}$

In one aspect, the above channel matching problem can be formulated in a bipartite graph. Referring to FIG. 15, consider a bipartite graph with two sets of vertices, C and H_(b). As shown, C represents the set of colors, and H_(b) represents the set of channel blocks. A weight from color c to channel block h_(b) may be defined as M_(c,h) _(b) (Equation 2). In one aspect, the matching may be such that the amount of overall transmission limitations imposed to different groups of devices based on their channel locations is minimized or reduced.

Once a bipartite graph is formulated, the techniques described herein can be used to find a match (from a color c to a channel block h_(b)) such that the cost metric (e.g., M_(c) ^(Ω)) for color c in a given matching assignment (e.g., Ω) is minimized. In one aspect, the network entity may minimize the cost function in Equation (3):

$\begin{matrix} {\min\limits_{\Omega \in {Matching}}{\sum\limits_{c = 1}^{C}{f\left( M_{x}^{\Omega} \right)}}} & (3) \end{matrix}$

Once such metric is defined, techniques presented herein can use an optimization algorithm (e.g., Hungarian algorithm) to solve the matching problem with complexity of O (H³). One example choice for the function f(x) may be ƒ(x)=10^(0.1x). However, other functions may be used. The goal of the channel matching may be to find a “fair” matching. In one example, a matching may be considered “fair” if no color (or orthogonal channel) is assigned a channel block (or location) that is unfairly limited by one or more of incumbent protection compared to other groups, maximum available bandwidth, maximum contiguous channel size, etc. FIG. 16 illustrates an example of a matching assignment determined by the network entity with and without function ƒ(x)=10^(0.1x). In the depicted example, assume C=2, H_(b)=2 and M_(1,1)=10, M_(1,2)=1, M_(2,1)=−10, M_(2,2)=−20 dB. Without function ƒ(x) above: M₁ ^(Ω)=10 and M₂ ^(Ω)=−20. On the other hand, with function ƒ(x) above: M₁ ^(Ω)=1 and M₂ ^(Ω)=−10.

In another aspect, the network entity may minimize the cost function in Equation (4):

$\begin{matrix} {\min\limits_{\Omega \in {Matching}}\max\limits_{c \in {\{{1,2,\ldots,C}\}}}M_{c}^{\Omega}} & (4) \end{matrix}$

Doing so may lead to more fairness. However, at the same time, the matching may be less efficient (e.g., compared to (3)).

As noted above, in some aspects, the network device may remove unusable channel locations from the assignment of channel locations to each of the number of orthogonal channels (e.g., blacklist unusable channels). As described below with respect to FIG. 17, in some aspects, after removing the determined unusable channel locations, the network device may determine an amount of bandwidth associated with each remaining channel location that is available for assignment. If the determined amount of bandwidth is below a threshold (e.g., BWmin), the network device may adjust at least one of one or more first parameters used for determining the number of orthogonal channels or one or more second parameters used for determining a number of the channel locations available for assignment.

The network device may adjust at least one of the number of orthogonal channels based on the adjusted first parameters or the number of channel locations based on the adjusted second parameters. The one or more first parameters may include at least one of a contour of a network graph used for determining the number of networks that have overlapping coverage, or an interference threshold used for determining the number of networks that have overlapping coverage. The one or more second parameters may include a threshold used for determining whether a channel location is unusable for the assignment. The number of orthogonal channels and/or the number of channel locations may be adjusted until it is determined that the amount of bandwidth associated with each channel location is above the threshold (e.g., BWmin).

In some aspects, once the determined amount of bandwidth is above the threshold, the network device may start with the largest possible size of channel blocks, do the assignment, decrease the size of the channel block, and repeat the procedure until it reaches the smallest channel block size (e.g., i=1). For example, as also described below with respect to FIG. 17, the assigning may include assigning first channel locations associated with a first maximum contiguous channel size to a first set of the orthogonal channels; after assigning the first channel locations, removing the assigned first channel locations from the available spectrum; after removing the assigned first channel locations, assigning second channel locations associated with a second maximum contiguous channel size (reduced to lower than the first maximum contiguous channel size) to a second set of the orthogonal channels; and repeating the procedure until the maximum contiguous channel size is at a threshold (e.g., i=1).

FIG. 17 illustrates an example flowchart 1700 for assigning channel locations to orthogonal channels, in accordance with certain aspects of the present disclosure. According to certain aspects, example operations 1700 may be performed, for example, by a network entity such as an eNB (e.g., eNB 106) which may be CBSD, a SAS (e.g., one or more of the SASs illustrated in FIG. 9), co-existence manager (CXM, or other network entity operating between SAS and CBSD (e.g., EMS illustrated in FIG. 9 or ASA controller 702 or 802 illustrated in FIGS. 7 and 8, respectively).

As shown, at 1702, the network entity may assign orthogonal channel(s) (e.g., color/label/shading) to networks based on a number of the networks that have overlapping coverage. At 1704, the network entity may perform blacklisting and determine U_(h). At 1706, the network entity may determine if BWmin is satisfied. If BWmin is not satisfied, the network entity may increase one or more thresholds (e.g., such as m_(c,h)) at 1708 and return to 1702. However, if BWmin is satisfied, at 1710, the network entity may determine i (for the largest possible channel block) and, at 1712, build channel blocks (H_(b) _(i) ). At 1714, the network entity determines if H_(b) _(i) is larger than C. If so the network entity, at 1716, performs the best matching and assigns each color one channel block and removes them from U_(h). Once the network entity determines that C is larger than H_(b) _(i) , the network entity determines, at 1718, whether i is greater than 1. If so, the network entity decrements i at 1720 and returns to 1710. If i is not greater than 1, the method ends.

FIG. 18 depicts an example of matching channel locations to two orthogonal channels, according to certain aspects of the present disclosure. In this example, C=2 (red (R) and green (G)) with U_(h) as shown. The network entity (at 1802) may start at i=3 (e.g., 15 MHz), and determine that a 15 MHz contiguous allocation is not possible. The network entity (at 1804) may then decrement i. For i=2, two channel blocks of 10 MHz can be built. The network entity (at 1804) may perform the best matching and assign each color (R and G) one 10 MHz channel block, and remove the assigned channel blocks from U_(h). The network entity (at 1806) may then repeat the best matching procedure for i=1. For example, as shown, three channel blocks of 5 MHz can be built. The network entity (at 1806) may assign each color one 5 MHz channel block. At the end of the matching, each color may be allocated 10+5 MHz.

FIG. 19 depicts an example of matching channel locations to two orthogonal channels, according to certain aspects of the present disclosure. In this example, C=3 (red (R), green (G) and orange (O)) with U_(h) as shown. For i=6,5, the network entity may determine (at 1902) that it is not possible to assign contiguous channel blocks. Subsequently, for i=4, the network entity may assign (at 1904) one channel block (20 MHz) for each color. Subsequently, for i=3,2, the network entity may determine that it is not possible to assign contiguous channel blocks. Subsequently for i=1, the network entity may assign (at 1906) two channel blocks (2*5 MHz) for each color, resulting in 20+5+5 MHz for each color.

Note that while the techniques herein refer to incumbent protection considerations for intra-GAA channel assignments, the techniques may also be applied to PAL protection considerations for intra-GAA channel assignment, incumbent protection consideration for intra-PAL channel assignment, joint incumbent and PAL protection consideration for intra-GAA considerations, and so on. Further, the above techniques can also be applied when quality of different channels are different for different groups of CBSDs due to, e.g., uncontrolled limitation (from higher priority tier protection), uncontrolled interference, etc.

Example Co-Existence Manager Consistency and Conflict Resolution

Aspects presented herein provide techniques for performing conflict resolution in situations where multiple network entities (e.g., CxMs, SASs, etc.) are managing one or more devices in the same (or overlapping) geographic area. In situations where multiple network entities cover the same geographic area, each network entity may independently assign channel locations to orthogonal channels used by different groups of wireless nodes in the geographic area.

Referring to FIG. 20, as a reference example, each network entity, at 2004, may build a network graph (e.g., a LTE-TDD overlap graph) and identify different LTE-TDD connected sets. The network entity may determine/generate the network graph based on information (e.g., list of LTE-TDD CBSDs, LTE-TDD spectrum, incumbent/PAL considerations, etc.) received at 2002. In some cases, the information received at 2002 may be received from another network entity (e.g., such as a SAS). At 2006, the network entity may color (e.g., assign an orthogonal channel to) each group of LTE-TDD CBSDs in a connected set. At 2008, the network entity may perform channel mapping for each group of LTE-TDD CBSDs in each connected set to assign channel locations to each of the orthogonal channels used by a group of LTE-TDD CBSDs in each connected set. Based on the channel mapping, the network entity may assign the channel locations to the orthogonal channels.

In situations where multiple network entities cover the same geographic area, there may be conflicts in the channel assignment results independently reached by one or more of the network entities. Referring to FIG. 21 as a reference example, assume there are two network entities, SAS1/CxM1 2102 and SAS2/CxM2 2104, managing the same geographic area that includes CBSDs 1-5. In this scenario, the channel assignment results of SAS1/CxM1 2102 may conflict with the channel assignment results of SAS2/CxM2 2104 if, as a result of the channel assignments, two or more interfering CBSDs are assigned to the same channel. For example, if CBSD1 is assigned to a first channel (by SAS1/CxM1 2102) and CBSD2 is assigned to the same first channel (by SAS2/CxM2 2104), the channel assignment results may conflict.

Accordingly, it may be desirable to provide techniques that can be used to ensure that channel assignment results from multiple network devices managing the same coverage area are consistent. Further, it may also be desirable to provide techniques that allow the network devices to perform conflict resolution in situations where the channel assignment results are not consistent.

FIG. 22 illustrates example operations 2200 for performing conflict resolution in a network managed by multiple network entities, in accordance with certain aspects of the present disclosure. According to certain aspects, example operations 2200 may be performed, for example, by a network entity such as an eNB (e.g., eNB 106) which may be CBSD, a SAS (e.g., one or more of the SASs illustrated in FIG. 9), co-existence manager (CXM), or other network entity operating between SAS and CBSD (e.g., EMS illustrated in FIG. 9 or ASA controller 702 or 802 illustrated in FIGS. 7 and 8, respectively).

Operations 2200 begin at 2200 where the network entity determines one or more first channel locations in order to assign at least a first orthogonal channel within the available spectrum, wherein each first orthogonal channel is associated with a group of one or more devices sharing bandwidth within one or more networks. In certain aspects, the determination of the first channel locations may be based on any of the techniques described above (e.g., operations 1100 in FIG. 11, operations 1700 in FIG. 17, operations 2000 in FIG. 20, etc.).

At 2204, the network entity participates in an exchange with at least a second network entity to share a first set of information associated with the first channel locations. In some aspects, the network entity may receive, from the second network entity as a part of the exchange, a second set of information associated with second channel locations that are determined by the second network entity in order to assign at least a second orthogonal channel within the available spectrum. At 2206, the network entity determines whether to modify at least a portion of the first set of information, based on the exchange.

The first set of information may include at least one of the determined first channel locations, a first network (coverage overlap) graph used to determine a first number of networks in the plurality of networks that have overlapping coverage, or the number of first orthogonal channels to assign to the group of devices. The second set of information may include at least one of the determined second channel locations, a second network (coverage overlap) graph used to determine a second number of networks in the plurality of networks that have overlapping coverage, or a number of the second orthogonal channels.

As part of the conflict resolution procedure, each network entity may independently determine channel locations to assign to a number of orthogonal channels. Referring to FIG. 20, as a reference example, each network entity may generate a network graph (e.g., at 2004), color the graph (e.g., at 2006), and perform channel mapping (e.g., at 2008). The network entity may then exchange its channel assignment results with one or more other network entities, and vice versa.

If there is no conflict between the channel assignment results, the network entity may refrain from performing a conflict resolution procedure to modify its channel assignment results (e.g., first channel locations). A conflict between channel assignment results may include at least one of the following: a conflict between network graphs (e.g., a first network graph may have a different overlapping coverage than a second network graph); a conflict between the coloring results (e.g., a difference in the number of determined orthogonal channels to assign to the groups of devices sharing bandwidth); or a conflict between the determined channel locations (e.g., assigned channel locations from the network devices are different).

If the network device determines there is a conflict between the channel assignment results, the network entity may proceed to perform a conflict resolution procedure to modify its channel assignment results. Based on the conflict resolution procedure, the network device may modify any of the information associated with the determined channel locations (e.g., at least one of the determined first channel locations, the first network graph used to determine a first number of networks in the plurality of networks that have overlapping coverage, or the number of first orthogonal channels to assign to the group of devices.

For example, if the network entity determines the coloring results are the same, the network entity may perform conflict resolution on the channel mapping step. Otherwise, if the network entity determines the network graphs are the same, the network entity may perform conflict resolution on the coloring results and determine the channel locations based on the changed coloring results. Otherwise, the network entity may perform conflict resolution on the network graphs and determine the channel locations based on the changed network graphs.

In some aspects, on-demand info-sharing on “detailed channel assignment results” can be supported upon request (e.g., for verification). In some aspects, if the network entity wishes to avoid conflict resolution, the (first) network entity can indicate to at least another (second) network entity (e.g., during the exchange of information) that the first network entity will accept a subset of or all of the “final” channel assignment results from the second network entity, and vice versa.

For the conflict resolution during channel mapping, an overall cost function may be defined based on one or more factors. These factors may include, e.g., an amount of transmission limitation imposed to a group of devices due to higher-tier protection, an amount of available bandwidth, the maximum contiguous channel size(s) desired by the network entities (e.g., eNBs or CBSDs), etc. The output results of the network entity with the smallest overall cost may be used by the conflict resolution mechanisms between the network entities to determine the channel mapping for each network entity. In cases, where multiple network entities have the same overall cost, the channel mapping of one of the multiple networks may be selected in an agreed non-biased manner (e.g., pseudo-randomly).

For the conflict resolution for the number of determined orthogonal channels to assign (e.g., the coloring step), if a single network entity is able to determine a smaller number of orthogonal channels (with a valid result), the result with the smallest number of orthogonal channels required may be selected. Otherwise, if the number of orthogonal channels required (determined by the two network entities) is the same, but the orthogonal channel assignments are different, the network entities may each select one of the orthogonal channel assignments from one of the network entities in an agreed non-biased manner (e.g., pseudo-randomly).

For the conflict resolution for the network graphs (e.g., in cases where there is disagreement on an edge in the graph), if all CBSDs of both vertices of an edge belong to a single network entity, that network entity's output can be selected to determine whether there is an edge. For the conflict resolution for the network graphs, an overall cost function may be defined based on one or more factors. These factors may include, e.g., an amount of transmission limitation imposed to a group of devices due to higher-tier protection, an amount of available bandwidth, the maximum contiguous channel size(s) desired by the network entities (e.g., eNBs or CBSDs), etc. The output results of the network entity with the smallest overall cost may be used by the conflict resolution mechanisms between the network entities to determine the network graphs for each network entity. Otherwise, the network entity may determine to place an edge if any network entity indicated the edge (e.g., conservative approach) or not place an edge if no network entity indicated the edge (e.g., aggressive approach).

As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “identifying” encompasses a wide variety of actions. For example, “identifying” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “identifying” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “identifying” may include resolving, selecting, choosing, establishing and the like.

In some cases, rather than actually communicating a frame, a device may have an interface to communicate a frame for transmission or reception. For example, a processor may output a frame, via a bus interface, to an RF front end for transmission. Similarly, rather than actually receiving a frame, a device may have an interface to obtain a frame received from another device. For example, a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for transmission.

The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software/firmware component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in Figures, those operations may be performed by any suitable corresponding counterpart means-plus-function components.

For example, means for determining, means for performing, means for transmitting, means for receiving, means for sending, means for signaling, means for selecting, means for correlating, means for evaluating, means for assigning, means for allocating, means for removing, means for summing, means for scaling, means calculating, means for averaging, and/or means for taking action, may include one or more processors, transmitters, receivers, and/or other elements of the user equipment 650 and/or the base station 610 illustrated in FIG. 6.

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or combinations thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, software/firmware, or combinations thereof. To clearly illustrate this interchangeability of hardware and software/firmware, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software/firmware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software/firmware module executed by a processor, or in a combination thereof. A software/firmware module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, phase change memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more exemplary designs, the functions described may be implemented in hardware, software/firmware, or combinations thereof. If implemented in software/firmware, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD/DVD or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software/firmware is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. 

What is claimed is:
 1. A method for wireless communication by a first network entity, comprising: determining one or more first channel locations to assign at least a first channel within available spectrum, wherein each first channel is associated with a group of devices sharing bandwidth within one or more networks; participating in an exchange with at least a second network entity to share a first set of information associated with the first channel locations; and determining whether to modify at least a portion of the first set of information, based on the exchange.
 2. The method of claim 1, wherein participating in the exchange further comprises receiving, from the second network entity, a second set of information associated with second channel locations determined by the second network entity to assign to at least a second channel within the available spectrum.
 3. The method of claim 2, wherein the at least first channel within the available spectrum and the at least second channel within the available spectrum are orthogonal channels.
 4. The method of claim 2, wherein the determination is to refrain from modifying the first set of information if there is not a conflict between the first set of information and the second set of information.
 5. The method of claim 2, wherein the determination is to modify at least the portion of the first set of information if there is a conflict between the first set of information and the second set of information, the method further comprising modifying at least the portion of the first set of information based on the determination.
 6. The method of claim 5, wherein: the first set of information comprises at least one of the first channel locations, a first coverage overlap graph used to determine a first number of networks in the one or more networks that have overlapping coverage, or a number of the at least first channel; and the second set of information comprises at least one of the second channel locations, a second coverage overlap graph used to determine a second number of networks in the one or more networks that have overlapping coverage, or a number of the at least second channel.
 7. The method of claim 6, wherein the modifying comprises modifying the first channel locations if there is a conflict between the first channel locations from the first set of information and the second channel locations from the second set of information.
 8. The method of claim 6, wherein the modifying comprises modifying the at least first channel if the number of the at least first channel from the first set of information is different than the number of the at least second channel from the second set of information.
 9. The method of claim 6, wherein the modifying comprises modifying the first coverage overlap graph if at least a part of the first coverage overlap graph is different from the second coverage overlap graph.
 10. An apparatus for wireless communications, comprising: at least one processor configured to: determine one or more first channel locations in order to assign at least a first orthogonal channel within available spectrum, wherein each first channel is associated with a group of devices sharing bandwidth within one or more networks; participate in an exchange with at least a second network entity to share a first set of information associated with the first channel locations; and determine whether to modify at least a portion of the first set of information, based on the exchange; and a memory coupled to the at least one processor.
 11. The apparatus of claim 10, wherein the at least one processor is configured to participate in the exchange by receiving, from the second network entity, a second set of information associated with second channel locations determined by the second network entity to assign to at least a second channel within the available spectrum.
 12. The apparatus of claim 11, wherein the at least first channel within the available spectrum and the at least second channel within the available spectrum are orthogonal channels.
 13. The apparatus of claim 11, wherein the determination is to refrain from modifying the first set of information if there is not a conflict between the first set of information and the second set of information.
 14. The apparatus of claim 11, wherein: the determination is to modify at least the portion of the first set of information if there is a conflict between the first set of information and the second set of information; and the at least one processor is further configured to modify at least the portion of the first set of information based on the determination.
 15. The apparatus of claim 14, wherein: the first set of information comprises at least one of the first channel locations, a first coverage overlap graph used to determine a first number of networks in the one or more networks that have overlapping coverage, or a number of the at least first channel; and the second set of information comprises at least one of the second channel locations, a second coverage overlap graph used to determine a second number of networks in the one or more networks that have overlapping coverage, or a number of the at least second channel.
 16. The apparatus of claim 15, wherein the at least one processor is configured to modify the first channel locations if there is a conflict between the first channel locations from the first set of information and the second channel locations from the second set of information.
 17. The apparatus of claim 15, wherein the at least one processor is configured to modify the at least first channel if the number of the at least first channel from the first set of information is different than the number of the at least second channel from the second set of information.
 18. The apparatus of claim 15, wherein the at least one processor is configured to modify the first coverage overlap graph if at least a part of the first coverage overlap graph is different from the second coverage overlap graph. 